Reassigned mobile message notifications

ABSTRACT

The instant application describes examples of managing a customer&#39;s mobile station and providing a notification of a resultant change. The disclosed examples provide for a subscriber device management application that executes on a customer&#39;s mobile device that allows changes to be made remotely to an operational control parameter of mobile station. In response to a change to the operation control parameter, a notification may be sent as a mobile messaging service message to a mobile station other than the customer&#39;s mobile station.

This application is a continuation of U.S. patent application Ser. No.12/712,804, filed Feb. 25, 2010, now U.S. Pat. No. 8,571,525, grantedOct. 29, 2013, the disclosure of which is expressly incorporated hereinby reference.

TECHNICAL FIELD

The present subject matter relates to techniques and equipment tointeract over the air with an application on a customer's mobile stationto remotely change a parameter of operation of the mobile station, e.g.to disable the mobile station and lock down the customer's personal datastored therein, and to provide a mobile messaging service notificationof the parameter change to another identified mobile station, such asanother station on the same mobile service account.

BACKGROUND

Advanced Devices (e.g., PDAs and Smartphones with open OS) are becomingmore poplar in both Consumer (including SMB) and Enterprise domains. Itha been predicted that this market segment will continue to experiencedouble-digit growth for the next 5 years. The Advanced Devices areplaying a more important role in the everyday life or a Consumer,Enterprise, Federal, and Government user.

As Advanced Devices are getting more popular, the complexity of reportedproblems, the number of support calls, and support call durations onthose devices continue to increase significantly, it is critical for aMobile. Service Provider (e.g., Verizon Wireless™) to provide improvedcustomer support and customer satisfaction more cost effectively.

Indeed, there is a need to reduce support cost and increase customersatisfaction with setup and troubleshooting experience associated withthe Advanced Devices problems by providing the necessary tools to thesupport teams in assisting to troubleshoot device configuration issuesefficiently. Specifically there is a need to enable remote management ofa mobile station (e.g., change the operational control parameters of thestation over the air) and to provide a notification of the change to theuser.

Additional advantages and novel features will be set forth in part inthe description which follows, and in part will become apparent to thoseskilled in the art upon examination of the following and theaccompanying drawings or may be learned by production or operation ofthe examples. The advantages of the present teachings may be realizedand attained by practice or use of various aspects of the methodologies,instrumentalities and combinations set forth in the detailed examplesdiscussed below.

SUMMARY

The technologies described herein enable management of a mobile station,e.g., to change an operating parameter of the station over the air, andto provide an associated notification of the change. For example, theinstant application describes a method of managing a customer's mobilestation and providing a notification of a resultant change. The methodincludes steps of communicating over the air through a mobilecommunication network with a subscriber device management applicationrunning on the customer's mobile station; causing the subscriber devicemanagement application to attempt to change an operational controlparameter of the customer's mobile station, via the over the aircommunication; and determining an outcome of the attempted change of theoperational control parameter of the customer's mobile station. Themethod also includes a step of sending a mobile messaging servicemessage, providing notification of the attempted change of theoperational control parameter of the customer's mobile station, throughthe mobile communication network to another mobile station associatedwith the customer.

The more specific examples in the detailed description may include oneor more of the following features. Determining the outcome of theattempted change of the operational control parameter of the customer'smobile station may include determining that the attempted change of theoperational control parameter of the customer's mobile station wassuccessful. The attempted change of the operational control parameter ofthe customer's mobile station may lock the customer's mobile station.The locking of the customer's mobile station may prevent access topersonal data of the customer stored in the customer's mobile station.Alternatively or additionally, the attempted change of the operationalcontrol parameter of the customer's mobile station may turn a built-incamera of the mobile station On or Off. Alternatively or additionally,the attempted change of the operational control parameter of thecustomer's mobile station may turn a Wi-Fi capability of the mobilestation On or Off. Alternatively or additionally, the attempted changeof the operational control parameter of the customer's mobile stationmay be directed toward troubleshooting the mobile station. Alternativelyor additionally, the attempted change of the operational controlparameter of the customers mobile station wipes out the content of themobile station. The wiping out of the content of the customer's mobilestation prevents access to personal data of the customer stored in thecustomer's mobile station. Determining the outcome of the attemptedchange of the operational control parameter of the customer's mobilestation may include determining that the attempted change of theoperational control parameter of the customer's mobile station wasunsuccessful.

In another general aspect, the instant, application describes a hostsystem for managing a customer's mobile station and providing anotification of a resultant change. The host system includes aprocessing device; and a memory storing executable instructions forcausing, the processing device to communicate over the air through amobile communication network with a subscriber device managementapplication running on the customer's mobile station; cause thesubscriber device management application to attempt to change anoperational control parameter of the customer's mobile station, via theover the air communication; determine an outcome of the attempted changeof the operational control parameter of the customer's mobile station;and send a mobile messaging service message, providing notification ofthe attempted change of the operational control parameter of thecustomer's mobile station, through the mobile communication network toanother mobile station associated with the customer.

The above general aspect may include one or more of the followingfeatures. The outcome of the attempted change of the operational controlparameter of the customer's mobile station may identify that theattempted change of the operational control parameter of the customer'smobile station was successful. The attempted change of the operationalcontrol parameter of the customers mobile station may lock thecustomer's mobile station. Locking of the customer's mobile station mayprevent access to personal data of the customer stored in the customer'smobile station. The attempted change of the operational controlparameter of the customer's mobile station may turn a built-in camera ofthe mobile station On or Off. The attempted change of the operationalcontrol parameter of the customer's mobile station may turn a Wi-Ficapability of the mobile station On or Off. The attempted change of theoperational control parameter of the customer's mobile station may bedirected toward troubleshooting the mobile station. The attempted changeof the operational control parameter of the customer's mobile stationmay wipe out the content of the mobile station. The wiping of thecontent of the customer's mobile station may prevent access to personaldata of the customer stored in the customer's mobile station. Theoutcome of the attempted change of the operational control parameter ofthe customer's mobile station may identify that the attempted change ofthe operational control parameter of the customer's mobile station wasunsuccessful.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 illustrates a functional block diagram useful in understandingnetworked elements/systems that may be used in causing a SubscriberDevice Management (“SDM”) application to change an operational controlparameter of a user's mobile station and notify the user of the same viaanother related mobile station.

FIG. 2 illustrates software and associated functionalities, in blockdiagram form, where the software may be run on the hardware of one ormore host or server type computers or systems of such computers, toimplement a customer communication system shown in FIG. 1.

FIG. 3A provides a high level illustration of a flow for an example of achange to an operational control parameter of a mobile station, as mightbe implemented in the system shown in FIG. 1.

FIG. 3B illustrates a SUM user interface used by Customer ServiceRepresentative (“CSR”) to change the operational control parameter ofthe mobile station.

FIG. 3C illustrates an Automated Customer Service System (“ACSS”) userinterface utilized by the user to change the operational controlparameter of the mobile station.

FIG. 3D illustrates a PDS user interface used by the CSR to change theoperational control parameter of the mobile station.

FIG. 4 illustrates a somewhat more detailed example of a procedure likethat of FIG. 3A.

FIG. 5 illustrates a process flow in more detail for a procedureassociated with partial locking of the mobile station.

FIG. 6A illustrates an exemplary request from a front end applicationfor locking operation.

FIG. 6B illustrates an exemplary SMS message that the customer receivesafter the lock operation is completed.

FIG. 7 is simplified functional block diagram of a computer that may beconfigured as a host or server, for example, to function as the MDMiserver in the system of FIG. 1.

FIG. 8 is a simplified functional block diagram of a personal computeror other work station or terminal device.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent to those skilledin the art that the present teachings may be practiced without suchdetails. In other instances, well known methods, procedures, components,and/or circuitry have been described at a relatively high-level, withoutdetail, in order to avoid unnecessarily obscuring aspects of the presentteachings.

Subscriber Device Management (“SDM”) is a client application thatremotely manages settings, configurations, and connectivity viaOver-the-Air (“OTA”) exchanges of a device (e.g., mobile phone) or thelike. When a device has the SDM application, a Customer ServiceRepresentative (“CSR”) can access the phone remotely. SDM may comepre-loaded on a mobile device. The mobile service provider manages SDMdevice data through the use of features. When a phone is provisioned onthe mobile service provider network, an SDM feature will be added to thedevice profile as an indicator that the device has the SDM client. Thisnew feature gives the customer service and technical supportrepresentatives the ability to make changes remotely to the device.

This ability can shorten the duration of support calls by avoidinglengthy and error prone user interactions where the CSR talks the userthrough an action via the device user interface (“UI”), the customerreads back a configuration parameter to CSR, and CSR talks the userthrough entering the correct information on the device etc, until anissue is successfully resolved. With this feature, the support staffalso can obtain faster access to more accurate and richer set of data tohelp with their troubleshooting, and remotely update the device withaccurate information. Overall, SDM improves the customers supportexperience and shortens the support call duration. Shortening theduration of support calls also translates to cost savings for the mobileservice provider. This capability could also lead to full customer selfservice for initial troubleshooting and diagnostics, even repairs, inthe future via web portal to reduce the number of service calls.

To illustrate a few examples, the SDM enable locking the mobile stationwhen the user loses his or her mobile station. That is, if a customersuspects that his or her station is lost or stolen or if a device cannotbe located, the customer cart request that a CSR lock or partially lockthe device to prevent an unauthorized use and to protect the privacy oftheir personal data. For another example, the SDM remotely enables Wi-Fior camera On/Off operations of the user's mobile station. This abilityhelps to reduce the amount of time between the CSR and customer that isneeded to find and read out the appropriate settings. Upon successfulchange (e.g., locking, partial locking, turning on/off camera) of theuser's mobile station, SDM provides notification of the change of theoperational control parameter through the mobile communication networkto another mobile station associated with the customer. For example, SDMenables sending a mobile messaging service message to another mobilestation when the above-requested lock operation is accomplished. Theuser can identify within his profile another number to which the SMSnotification message can be sent. Then once the mobile phone, forexample, is locked, the SMS message will be sent to that number. This isan improvement over the prior art because previously the user had towait to receive this change notification information via mail or e-mail.

With this overview, the SDM and notification will be described in moredetail respect to the following figures. FIG. 1 illustrates a functionalblock diagram useful in understanding networked elements/systems thatmay be used in causing SDM application to change an operational controlparameter of the user's mobile station and notify the user of the same.A mobile communication network 10 may be operated by a carrier orservice provider to provide a wide range of mobile communicationservices and ancillary services or features its subscriber customers andassociated mobile station (“MS”) users. The elements generally indicatedby the reference numeral 10 generally are elements of the network andare operated by or on behalf of the carrier, although the mobilestations typically are sold to the carrier's customers. The mobilecommunication network 10 provides communications between mobile stationsas well as communications for the mobile stations within networks andstations 11 outside the mobile communication network 10.

For purposes of later discussion, several mobile stations appear in thedrawing, to represent examples of the mobile stations that may receivevarious services via the mobile communication network 10. Today, mobilestations typically take the form of portable handsets, smart-phones orpersonal digital assistants, although they may be implemented in otherform factors. For discussion of some of the notification scenarios, wewill assume that the mobile stations 13, 15 and their associated MDNsare all covered under one subscriber account, and that among thosestations, the mobile station 13 is the station of the account holder(“AH”).

The network 10 allows users of the mobile stations to initiate andreceive telephone calls to each other as well as through the publicswitched telephone network (“PSTN”) and telephone stations connectedthereto. The network 10 allows SMS type text messaging between mobilestations and similar messaging with other devices via the Internet. Thenetwork 10 typically offers a variety of other data services via theInternet, such as downloads, web browsing, email, etc.

The mobile communication network 10 typically is implemented by a numberof interconnected networks. Hence, the overall network 10 may include anumber of radio access networks (“RANs”), as well as regional groundnetworks interconnecting a number of RANs and a wide area network(“WAN”) interconnecting the regional ground networks to core networkelements, such as the MMSCs. A regional portion of the network 10, suchas that serving mobile stations 13, 15 will typically include one ormore RANs and a regional circuit and/or packet switched network andassociated signaling network facilities.

Physical elements of a RAN operated by one of the mobile serviceproviders or carriers include a number of base stations represented inthe example by the base stations (BSs) 19. Although not separatelyshown, such a base station 19 typically comprises a base transceiversystem (“BTS”) which communicates via an antennae system at the site ofbase station and over the airlink with one or more of the mobilestations 13, 15, when the mobile stations are within range. Each basestation typically includes a BTS coupled to several antennae mounted ona radio tower within a coverage area often referred to as a “cell.” TheBTS is the part of the radio network that sends and receives RF signalsto/from the mobile stations that the base station currently serves.

The radio access networks also include a traffic network representedgenerally by the cloud at 21, which carries the user communications forthe mobile stations 13, 15 between the base stations and other elementswith or through which the mobile stations communicate. Individualelements such as switches and/or routers forming the traffic network 21are omitted here for simplicity.

A Mobile Directory Number (“MDN”) or Mobile Telephone Number (“MTN”) isthe telephone number assigned to a mobile station, which a calling partyor device inputs in order to call or send a message to the particularmobile station. To call the mobile station 15, for example, a use of aPSTN telephone or of another mobile station dials the MDN associatedwith the mobile station 15. To send a MMS message or a SMS message todestination mobile station 15, as another example, typically entailsinput of the MDN of that mobile station. A Mobile Identification Number(“MIN”) is an identification number used by the network 10 to signal aparticular mobile station. The MIN is formatted like a telephone number,and the MIN may be the same as the MDN. However, increasingly, thenetwork assigns a different number for use as the MIN and translates theMDN input by a calling or other originating party into the MIN that thenetwork 10 uses to establish the call or send the message to thedestination mobile station. Of these numbers assigned to the mobilestation, the MDN typically is the number or address of the station knownand used by other parties or stations and is the number or address ofthe mobile station that appears in billing and account records and isaccessible via web site or call-in account services.

The traffic network portion 21 of the mobile communication network 10connects to a public switched telephone network 23. This allows thenetwork 10 to provide voice grade call connections between mobilestations and regular telephones connected to the PSTN 23. The drawingshows one such telephone at 25. For purposes of discussingnotifications, some notifications may entail voice message delivery oreven service representative calls to the account holder, for example, ata regular telephone such as telephone 25 via the PSTN 23. The PSTN 23also provides connections to other types of customer premises equipment,such as facsimile or FAX machines. The drawing shows one FAX machine 27,by way of example, to illustrate the point that a subscriber or accountholder notification may entail a facsimile transmission of thenotification message to the subscriber's FAX machine, such as themachine 27.

The traffic network portion 21 of the mobile communication network 10connects to a public packet switched data communication network, such asthe network commonly referred to as the “Internet” shown at 29. Packetswitched communications via the traffic network 21 and the Internet 29may support a variety of user services through the network 10, such asmobile station communications of text and multimedia messages, email,web surfing or browsing, programming and media downloading, etc. Forexample, the mobile stations may be able to receive messages from andsend messages to user terminal devices, such as personal computers,either directly (peer-to-peer) or via various servers (not, separatelyshown). The drawing shows one such user terminal device as a personalcomputer (“PC”) at 31, by way of example. For purposes of discussingnotifications, some notifications may entail an email messagetransmission of the notification to the subscriber's data terminal, suchas to the PC 29 via the Internet 29.

Wireless carriers developed the short message service (“SMS”) totransmit text messages for display on the mobile stations. In manyexisting network architectures, the SMS traffic uses the signaling,portion of the network 21 to carry message traffic between a ShortMessage Service Center (“SMSC”) 33 and the mobile stations. The SMSCsupports mobile station to mobile station delivery of text messages.However, the SMSC also supports communication of messages between themobile stations and devices coupled to other networks. For example, theSMSC 33 may receive incoming IP message packets from the Internet 29 fordelivery via the network 21, one of the base stations 19 and a signalingchannel over the air link to a destination mobile station. For thislater type of SMS related communications, the network 10 also includesone or more Short Message Peer-to-Peer (SMPP) protocol gateways 34. TheSMPP gateway provides protocol conversions, between SMPP as used by theSMSC 33 and the protocols used on the Internet 29 or other IF network.SMPP messages ride on IF transport, e.g. between the gateway 34 and theSMSC 33.

Of note for purposes of this discussion, the system 10 supports serviceor account related notifications to end users, for SDM related changenotifications and for a variety of other notifications that the serviceprovider may want to send its customers. Many of the notificationsherein are sent to various mobile stations using SMS capabilities of thenetwork 10. For example, when there is a chance in a subscriber'saccount warranting notification, then the network 10 will provide anappropriate notification in the form of an SMS message sent via the SMPPgateway 34, the SMSC 33, the traffic network 21, one of the basestations 19 and a signaling channel over the air link to the mobilestation 13 of the subscriber/account holder. For some notifications, thesystem 10 may determine if the SMS transmission successfully providednotification to the mobile station 13, and if not, initiate one or morealternative notification procedures to other destinations designated forpossible notice to the particular subscriber/account holder. Thesemessaging capabilities also provide transport for notifications of SDMrelated changes.

The carrier will also operate a number of systems that provide ancillaryfunctions in support of the communications services provided through thenetwork 10, and those elements communicate with other nodes/elements ofthe network 10 via, one or more private IP type packet data networks 35(sometimes referred to as an Intranet). The support elements, forexample, include one or more systems of record, such as the system shownat 39. An example of such a system 39 is a billing system, whichincludes subscriber account records. A large carrier typically has anumber of such systems, and the system that stores the account data fora particular subscriber may be referred to as the “system of record” forthat subscriber's account.

The exemplary network 10 also includes a customer communications system41, which is coupled for communication via the private network 35. Thecustomer communications system 41 receives notification requests fromvarious other carrier systems and generates and sends the requestednotifications. In some cases, the system 41 also updates information insystem(s) of record, as part of its processing in response to thenotification requests.

At least some notification requests may be generated upon change to anoperational control parameter of the customer's mobile station. Forexample, the change may include locking or partial locking, the mobilestation remotely or turning the camera on/off on the mobile stationremotely. The customer communications system 41 may generate and sendSMS messages, typically including at least one to the mobile station 13designated as that of the account holder, in response to such a changein the examples discussed in more detail below, the customercommunications system 41 also supports alternative messaging, forexample, in the form of facsimile, voice or email messages, and/orletter mailings which are used for changing an operational controlparameter of the customer's mobile station.

In practice today, the carrier will also offer its subscribers on-lineaccess to a variety of functions related to the subscribers' accounts,such as review of billing statements and usage data, on-line payment,subscription changes, password control or the like. For that purpose,the carrier in our example operates a customer account web server 43,offering a ‘My Account’ (Now My Verizon) type subscriber interface viathe Internet. Hence, a user's terminal, such as PC 31, may be used toaccess on-line information about a subscriber's account, which themobile carrier makes available via the carrier's My Account web siteaccessible through the Internet 29. Of note for purposes of the presentdiscussions of notifications, the web site provides secure user accessto enter and/or otherwise change various aspects of the subscriber'saccount related information. The website also may allow the subscriberto designate the MDN for the account holder's mobile station 13 and/oran MDN of a device to receive notification of a SDM related parameterchange.

With that overview of the system, it may be helpful now to consider ahigh-level discussion of an example of a change to an operationalcontrol parameter of the customer's mobile station and attendantnotification and update, including how these services might appear fromthe user or subscriber's point of view. The management of SDM featureresides in the customer-facing service layer, which consists of MyAccount and Automated Customer Service System (“ACSS”) server. TheSDM-capable mobile stations may be pre-loaded with proper SDM clientapplication and provisioned via a Mobile Device Managementinfrastructure (“MDMi”) server 51.

The MDMi server 51 communicates with the SDM client on the mobilestation (e.g., mobile station 13) to implement the operational controlparameter change thereto. The MDMi server 61 may be indirectly accessedby the customer or the CSR. For example, the customer may indirectlyaccess the MDMi server 61 via My Account or My Business application onthe website server 43. The My Account application allows customers toperform self-service functionality on their accounts and may be accessedvia the personal computer 31. The My Business application allowsbusiness customers to perform self-service functionality on theiraccounts.

In one specific example, a customer calls a CSR for mobile issues (e.g.,to change or configure an operational parameter of a mobile station).The call may be from the mobile station or from another telephone. TheCSR or the Interactive Voice Response (“IVR”) will explain the SDMbenefits and ask the caller to accept the SDM profiling session forexample, press 1 for yes and press 2 for no). Assuming that this actionis performed by the IVR, the acceptance (or rejection) information willbe passed to CSR. If it is accepted, the next available CSR willinitiate the SDM profiling. The CSR may perform the SDM profilingthrough ACSS server 62, which provides a front-end application toindirectly access the MDMi server 61.

After the CSR initiated an SDM profiling, an UI screen will be sent tothe user asking for permission for profiling his/her mobile. Thecustomer can either accept or reject the SDM profiling. This process mayoccur every time the user calls the CSR for help on the user's mobilestation. It the user accepts the SDM profiling, the CSR can query andread SDM parameters and write certain parameters to performtroubleshooting and make corrections. If the CSR finds any parameter orsetting is incorrect and needs to be corrected, before he/she make acorrection, an UI screen may appear asking the permission to overwritethe Incorrect parameters or settings. The user can either accepts orrejects the proposed correction.

Should the user reject the SDM profiling, the CSR can only lead the userstep-by-step manually to troubleshoot the device. If the CSR finds anyincorrect parameters or setting, be/she can suggest the user to make achange. The user can elect to accept or reject the CSR's suggestion. Ifusers have their My Account set up properly, they can use My Accountportal via the web to perform a change to an operational parameter ofthe mobile station instead of using the CSR.

My Account, for example, provides control over the partial locking andunlocking, operation of the mobile station. The User's acceptance orrejection of SDM services at any time will not affect the user's abilityto exercise these options. Additionally, should the user reject the SDMservice during a troubleshooting call, the action will not affect thepresence of the SDM application on the mobile device. My Account,however, does not control all of the operational parameters of themobile station. For example, My Account may not have the control overbuilt-in camera on/off or Wi-Fi radio on/off.

The subscriber may use the PC 31 (or web enabled mobile station, etc.)to log-in the subscribers account via, the site offered by the server 43to chance the operational parameter of the mobile station (e.g., partiallocking of the mobile station). In operation, the subscriber would usetheir User ID and a password to log onto their own account page at thecarriers website, after which, the subscriber can revise existingoperational parameter of the mobile station.

Once the operational change is made to the mobile station, the MDMiserver 61 sends a notification request to the customer communicationssystem 41, which will cause the system 41 to send one or morenotifications. The CCC request processor in customer communicationssystem 41 may initially generate an SMS message to notify thesubscriber. The SMS message may be sent to a previously designatedaccount holder MDN. Alternatively or additionally, the SMS message maybe sent to an MDN of the mobile station in which the operational controlparameter was changed. Alternatively or additionally, the SMS messagemay be sent to an MDN associated with another mobile station. Thislatter feature enables promptly notifying the user of the changes madeto the user's mobile station in cases where the user's mobile station islost or stolen, which is an improvement over the prior art becausepreviously the user had to wait to receive such information via mail ore-mail.

The CCC may glean the information identifying the destination of the SMSmessage from the subscriber's record stored in server 39 or thesubscriber's preferences 59. For example, the subscriber may identifywithin his profile another number to which the SMS message can be sentand then once subscriber's phone, for example, is locked, the SMS willbe sent to that number. To illustrate further, the subscriber mayrequest that the SMS message be sent to the subscriber's relative mobilestation when the subscriber's mobile station is locked, for example. TheCCC may receive the information identifying the destination of the SMSmessage directly from the subscriber during the request for theoperational change to the mobile station.

FIG. 2 depicts software and associated functionalities, in block diagramform, where the software may be run on the hardware of a host or servertype computer or system of such computers, to implement the customercommunication system 41; and that drawing illustrates several otherelements that communicate with that system for providing notificationsto mobile users, including those provided when there is a change in anoperational control parameter of the mobile station via the SDMapplication. For example, the drawing shows the systems of record 39 and53, in this case the billing system 39 and the preference center 53 theexample, the customer communication system is implemented as anenterprise middleware web service written in Java that receivesnotification requests in the form of XML via HTTP or MQ, and followsbusiness rules to send customer notifications and update systems ofrecord. In general these communications may utilize the CCES webservices to facilitate the sending of text message, Email, letter, andfax notifications. Hence, the customer communication system 41 may beimplemented as middleware, that is to say, in this example, as softwarefor implementing a CCC notification request processor 47, one or moredatabases 49 and 51, and a directory 53, as will be discussed in moredetail below.

Although shown as a common platform at 41 in FIG. 1, the elements of thecustomer communication system 41 of FIG. 2 may be implemented onseparate hardware communicating with each other via a network the sameas or similar to network 35. For example, one or more of the databases49, 51 and 53 typically will be implemented as separate servers incommunications with the hardware platform(s) implementing the CCCnotification request processor 47, although the databases may beimplemented as records and appropriate application software running onthe same computer as the middleware for the CCC notification requestprocessor 47. The preference center directory 53, for example, may beimplemented as a LDAP server coupled for communication with the computerrunning the CCC notification request processor 47 programming.

The CCC notification request processor 47 receives notificationrequests, processes them and provides the processed requests toassociated messaging applications that send the desired notificationsout via one or more delivery techniques. In the illustratedimplementation, the CCC notification request processor 47 provides suchnotification services for a number of enterprise applications,particularly account change notifications. For example, enterpriseapplications such as My Verizon running, on the web server 43 maytrigger notifications of certain activities on a subscriber's mobilestation, such as when a customer uses the on-line Web service throughserver 43 to change the operational control parameter on thesubscriber's mobile station. In any such ease, the CCC request processor47 will send a notification to the customer following specificnotification logic and provide fallout files by area when thenotification cannot be made.

The customer communication system 41 will include or have communicationaccess to a number of databases that store information used inperformance of various notification related functions, in the example,the customer communication system 41 includes a database 49 of businessrules and a database 51 of notification message templates. The rules inthe database 49 provide the logic for determining what notifications tosend in response to the various Customer Propriety Network Information(“CPNI”) changes made on enterprise applications. The rules in thedatabase 49 also provide the logic for determining what notifications tosend in response to the various SDM related changes to the mobilestations. The template database 51 provides the format and commoncontent, e.g., forms or templates, for the various notification messagessent out by the system 41.

The Preference Center is the system of record for communicationpreferences and account holder designation. Communications with thissystem of record 53 provide the CCC request processor 47 withinformation that is useful in processing of various notifications,including notifications regarding account. The systems 53 and 41communicate using XML, via the network 35, to store and retrieve thepreference and account holder data from system 53.

Thus, the preference center directory 53 stores preference dataregarding notifications for various network customer accounts that maybe subject to notifications. The preference center directory 53, forexample, stores the MDN of the account holder as designated by thesubscriber. Similarly, the preference center directory 53 may store theMDN of the mobile station on which the subscriber would like to receivethe SDM related change notifications. The directory may store othernotification preference information for the subscriber account, foraccount change notifications and/or for other notifications that thecarrier may want to provide to the subscriber, such as for example,notification related, to a change in operational control parameter ofthe customer's mobile station. The language for the notification alsomay be specified by a field, e.g., as provisioned in the web server. TheCCC request processor 47 communicates with the Preference Centerapplication that updates its directory 53 using the LightweightDirectory Access Protocol (LDAP).

The customer communication system 41 also runs one or more messageoutput applications, identified as CCES applications in FIG. 2, forprocessing the notification request messages output from the CCCnotification request processor 47, as needed to generate and send theactual notification messages through one or more communication deliverychannels. The CCC notification request processor 47 modifiesnotification request messages based on its processing and outputs themodified notification request messages in XML format to the appropriateone or more of the CCES applications, to send the actual notifications.The CCES applications comprise application programming software, whichmay run on the same or a different computer from the CCC notificationrequest processor 47.

The CCES applications enable the customer communication system 41 toprovide notifications, including notifications regarding accountchanges, and notifications for changes to operational control parametersof the mobile station, using a number of communication techniques, asshown by way of example to the right of FIG. 2. Some messages may bebatch processed for SMS communications or sent in real time in responseto triggering events as represented by the My Account SMS processing inthe drawing. Batch SMS communications may be limited to business how'sif desired or sent at any time of the day. Event responsivenotifications, such as those for the account change notifications, wouldbe sent in real-time as the change events are detected and processedthrough the customer communication system 41. The customer communicationsystem 41 also supports other types of notifications, such as email,letter, or facsimile transmissions via an Enterprise CommunicationServices (“ECS”) function.

The customer communication system 41 could be implemented on a singlehardware platform. However, to provide effective notification servicesfor a large number of customers and a large volume of trigger events orenter rise applications requiring notification, including variousaccount data changes, the customer communication system 41 may utilize adistributed system architecture. The exemplary system architecture willbe highly available and fault tolerant. Those skilled in the art willrecognize, however, that other system architectures may be used e.g., tomeet the demands of increased event and notification traffic for accountchanges and/or other enterprise applications that require customernotifications.

The CCES software for notification services may be written in Java. EachCCES Notification Server node in the example has an instance, ofWebsphere running the CCES notification software and theCCC/MyAccountSMS software on the same Java Virtual Machine (“JVM”). Thisallows the account change notifications to utilize all of the featuresof the customer communication system including; SMS notifications, EMSnotifications, Email notifications, fax notifications, letternotifications, notification templates, rules based failurenotifications, preference center lookups, and weekly reports. EMS(Enhanced Messaging Service) is an application-level extension to ShortMessage Service (SMS) for cellular phones available on GSM, TDMA andCDMA networks. The CCC software, for example, makes the preferencecenter lookups on the account number provided in the notificationrequest to send SMS notifications to the Account Holder. The CCCsoftware also updates preference center records for subscribers toreflect account changes, responsive to the account registration andchange notification requests.

The flow chart of FIG. 3A provides a high level illustration of a flowfor an example of a change to an operational control parameter of amobile station, as might be implemented in the system 10. FIG. 4 shows asomewhat more detailed exemplary procedure. As noted above, thesubscriber can utilize the My Verizon web site functionality via theserver 43 to change the operational control parameter of the mobilestation or can implement such as change via the CSR, although in thisexample some of the changes may only be implemented via the CSR such as,for example, turning the built-in camera on/off or turning the Wi-Fion/off. The changes to the operational control parameter of the mobilestation may include full/partial locking, unlocking of the mobilestation, wiping out the content of the mobile station, turning on/offthe built-in camera or the Wi-Fi of the mobile station. In oneimplementation, when the CSR, is utilizing the SDM application to changeconfiguration of the mobile device, only the pertinent device andapplication configuration parameters are intended to be viewable by theCSR. For example, no user generated content such as, for example,contact information, messages, e-mails, pictures or video can beaccessed or viewed by the CSR.

When a user calls a CSR with a mobile station related issue or becausethe user has lost the mobile station, the CSR who is assisting the userwill obtain the user's permission to initiate a call to the mobilestation to perform one of many available operations. The CSR may solicitthis permission via a front end application such as, for example, Pointof Sale (“POS”), ACSS, or SDM user interface. FIG. 3B illustrates a SDMuser interface used by CSR to change the operational control parameterof the mobile station. FIG. 3C illustrates a ACSS user interfaceutilized by the user to change the operational control parameter of themobile station. FIG. 3D illustrates a POS user interface used by the CSRto change the operational control parameter of the mobile station.

Once the front end application receives the request, it submits therequest to the SDM IT Enterprise Service Bus (“ESB”) (310). The SDM ITESB will transform the request to send it to VZGAPS platform (312). Forexample, the SDM IT ESB transforms the request front XML ever HTTP intoXML over MQ and sends it to network. The network receives the requestand forwards it to the MDMi server 61 (314), in response, the MDMiserver 61 locates the mobile station and initiates action (316). Forexample, if the request is to lock the mobile station, the MDMi server61 performs the lock Operation. The MDMi server 61 sends the result backto the network (318), which in turn forwards the response to the SDM ITESB (320). The SDM IT ESB then sends the response back to the requestingfront end application (322), which displays the result to the user(324).

As shown in FIG. 1 multiple front end applications will offer thisservice to the mobile service provider's customers. In one example, theACSS application 62 is used by the customer hieing personnel. The MyAccount 43 is a self-service vehicle that the mobile service providerprovides to the customers to take care of the requests without having tointeract with the CSR.

FIG. 4 illustrates a somewhat more detailed procedure for changing theoperational control parameter of a mobile station, as might beimplemented in the system 10. The process 400 begins with the customercontacting the CSR and requesting a change to an operational controlparameter of the mobile station (410). The change to the operationalcontrol parameter may include for example partial/full locking,unlocking, of the mobile station, turning the built-in camera or theWi-Fi on/off, and/or wiping the data inside the mobile station.Alternatively, the change to the operational parameter may include oneor more changes associated with troubleshooting the mobile station orresetting the mobile station to the original factory setting.

Upon receiving the request, the CSR verifies the customer and accountinformation (412). The CSR confirms that the caller has the authority tomake changes on the mobile service provider account. The CSR alsoconfirms that the station has the SDM client and obtains the customer'sokay to make the requested changes using SDM functionality. Using theSDM client, the CSR makes the requested operational control parameterchange (414). The CSR selects the option best suited towards thecustomer's needs. For example, if the customer's station is lost orstolen, the CSR would select “Lock” in the front end application asshown in FIG. 3B. Toward this end, the CSR may ask the customer if thecustomer would like to receive the result of the operation as an SMSmessage to another mobile number on his/her account. The customer may bepleased with this capability and may respond yes. For example, thecustomer may respond “Yes, please have it go to my wife's number.” Inresponse, the CSR selects “the wife's number” to receive the SMS.

The front end application sends the request to the SDM IT ESB with themobile number to implement the Lock operation, and the mobile number toreceive the notification (416). The mobile number to receive thenotification may be included in the transaction. The SDM IT ESBtranslates the operation request to send to network (418). The networklocates the station to be changed and sends the requested operation tothe station (420). In one example, the network locates the mobilestation via the MDMi server which instructs the mobile station to makethe operational control parameter change. The mobile station receivesthe request, processes it, and sends the response to network (422),which in turn sends the response to the SDM IT ESB (424). The responseindicates the operation success or failure.

The SDM IT ESB transforms the response and sends it to the front endapplication; the SDM IT ESB also sends a request to the CCES applicationto send out the notification to the selected, mobile number (426). Thefront end application receives the result (428). The GOES also receivesthe request and forwards the result to the mobile number provided by thefront end application (430). In keeping with the previous example, theCCES forwards the result to the customer's wife mobile number. As such,the customer receives an instantaneous SMS that the operation wassuccessful (or failed) on his wife mobile station. Of course, the CCEScan also forward the message to the customer via e-mail or mail. As aresult of this operation, the customer is impressed, and happy, to havegotten an automatic update even though his mobile device may not beavailable to receive the notification. This, for example, helps relievethe anxiety of not knowing who might find the lost phone and have accessto his information.

As noted above, one example of the above operational control parameterincludes partial luck/unlock of the mobile station. FIG. 5 illustratesan exemplary process 500 that describes in more detail the procedureassociated with partial locking of the mobile station. Due to thesimilarity between partial lock and voluntary suspend, however, thisdisclosure first provide the summaries for these two features and thedifferences between them and then describes the partial lock process 500in detail.

Voluntary suspend is a back-end solution from the network, which blocksthe service to the mobile station. A station associated with a suspendedaccount cannot make outgoing calls (except for 911) or receive incomingcalls. However, the station is not protected from unauthorized access,if the station is not password protected. If the station does not havepassword protection, the station content can be accessed by anyone.Additionally, if the station is the primary line in a Familyshare plan,the suspension will affect all lines within this plan.

SDM lock is a device-based feature. A locked device cannot make outgoingcalls (except for 911); however, it can receive incoming calls. If auser suspects his/her device is lost or stolen, he/she could elect topartially lock the device to protect the privacy of their personal dataand to prevent an unauthorized use. A user can lock his/her device withpartial lock, and then call the device and the ringing/vibration mayreveal the physical location of the device. A partially locked devicecan make an emergency call and receive an emergency call back, calls tocustomer service (611 and *228, for example), receive in-coming calls,and participate in SDM activities.

Key differentiators between the voluntary suspend and the SDM lock isthat SDM Lock offers the user a better chance to recover the lost phoneby calling the lost device—its ringing/vibration may lead the owner tofind it, or a person is taxi driver, a restaurant waiter/waitress, forexample) whoever finds it can answer the phone. Additionally, thecontents stored in the device built-in memory will be protected fromunauthorized access. The voluntary suspend can be used as a lastresource, if a device is not reachable by the network to perform lock.

The partially locked device may be unlocked via the unlock feature. Thepartial lock and unlock operations utilize the standards based approachto first send the device an SMS notification. The device will setup adata connection with the server for a two-way authentication thenproceed with the partial lock or unlock operation. When completed, thedevice will report back to the server with status. If the device failsto establish a data connection to communicate to the server, it willfallback to support a SMS only partial lock or unlock. This approach isto maximize the success rate of the partial lock, and unlock operationsfor devices without data roaming.

The partial lock operation may be performed by visiting a web portal(e.g., My Account), calling CSR, or seeking in store support. FIG. 5illustrates a process 500 for performing the lock operation via callinga CSR. The process 500 begins with the subscriber calling a CSR todisable a lost or stolen mobile station (510) with the CSR logged into afront end application (512). The CSR authenticates the caller as anaccount owner and pulls up account information (514). The CSR identifieswhether the mobile station includes a SDM application (516). If not(516, no), the CSR follows the standard lost or stolen path (518). Ifyes (516, yes), the CSR may suspend the standard lost or stolen path(520) and may instead seek the customer's consent to perform the partiallock using the SDM application (522). For example, the CSR may explainthe SDM benefits and ask the caller to agree with making the changethrough the SDM application. To this end, the CSR may check whetherthere is a charge to the customer for the partial lock feature. If so,the CSR informs the customer of the same. In one example, the CSRdetermines that there is a $1.99 charge and informs the customer of thecharge, which will appear in his/her monthly bill.

Assume for discussion that the customer agrees with the charge andselects another mobile number to receive SMS notification (524). Oncethe customer agrees with the charge, the CSR may seek confirmation andthe customer again confirms the customer's desire to lock the device atthis point in time. In response, the CSR initiates the lock operationand selects the MDN to receive the notification (526). The execution ofpartial lock functionality may happen silently (user acceptance may notbe required).

The front end application sends a lock operation request with the MDN ofthe impacted mobile station and the MDN of the mobile station selectedfor SMS notification to the SDM IT ESB (528). FIG. 6A illustrates anexemplary request from the front end application for a lockingoperation. The SDM IT ESB sends response to front end application thatthe request was received (530), and sends the request to the network(532). The network receives the request, locates the impacted mobilestation, locks the impacted mobile station, and sends the result back tothe SDM IT ESB (534). Specifically, the network forwards theinstructions for locking the impacted mobile, station to the MDMiserver. The MDMi server locates the mobile station and sendsinstructions to the SDM application of the mobile station to lock themobile, station. The SDM application receives the instructions,initiates the lock operation, and sends the result (e.g. success orfailure) back to the network through the MDMi server.

The SDM IT ESB receives the response from the network (536), and sendsthe MDNs for the impacted mobile station, and mobile, station for SMSnotification to CCES to send SMS (538) and sends the request completionstatus to the requesting front end application. The CCES sends an SMSnotification message regarding impacted mobile station to the mobilenumber that the customer selected (540). As such, the customer receivesan instantaneous SMS message that the operation was successful (orfailed) (542). FIG. 613 illustrates an exemplary SMS message that thecustomer receives after the lock operation is completed. If the partiallock operation is successful, the charge will be placed in thesubscriber's monthly bill. In this manner, the user who has lost his/herdevice can call the lost device and hopefully find the device from itsringing or vibration. Meanwhile the device, contents are protected.

In a slightly different implementation, the CSR front end processdetermines (per the aforementioned business rules) that subscriber iseligible for free of charge partial lock feature. The CSR informs thesubscriber that his/her device can be partially locked free of chargeand the resulting effects or a locked device. The subscriber agrees topartial lock the device. The CSR performs the partial lock on thedevice, and the SDM server confirms the operation. The CSR informs thesubscriber that the partial lock operation is successful and informs thesubscriber that an email notification will be sent to the account holderand authorized users. CSR also asks the subscriber if he/she wants tosend an optional SMS message to another mobile, which is listed, underhis/her account if the subscriber has another mobile station listed,he/she can choose one so that an SMS message can be sent to notify thesubscriber about the SDM partial lock successful for failed) execution.

The partial lock operation may also be performed through the web portal.For example subscriber can log into My Verizon thorough PC 31 to partiallock his/her device. The subscriber or account holder is properlyauthenticated to access the account information. Thereafter, the MDN isproperly entered for the lost/stolen device. When the subscriber oraccount holder clicks “Lock” button, the web portal will check thebusiness rules (directly or indirectly via other systems) to determineif this subscriber is eligible for free of charge partial lock feature.An UI screen may display “Processing . . . ” In one example, the systemdetermines that this subscriber or account holder is not eligible forfree partial lock. An UI screen will display “You are about to Lock yourmobile device. This service will charge $1.99 to your monthly bill. Doyou accept this charge? Okay or Cancel.” If Cancel button is selected,the lock operation will not take place. The subscriber or account holderreturns to the previous web page. If Okay button is selected, the systemwill trigger the partial lock operation at the SDM server, which willperform the partial lock operations. An UI screen may display “Lock inProgress” during the process. After the sum server receives the partiallock successful completion confirmation, an UI screen may display withthe transaction confirmation.

In a slightly different implementation utilizing My Verizon, the webportal determines that the subscriber or account holder is eligible forfree of charge partial lock feature. An form screen may display “You areabout to Lock your mobile device. Okay or Cancel.” Similar to theprevious example, if Cancel button is selected, the lock operation willnot take place. The subscriber or account holder stays in the previousweb page. The UI also asks the subscriber if he/she wants to send anoptional SMS notification message to another mobile station, which islisted under his/her account if the subscriber has other mobile stationlisted, he/she can choose one so that an SMS notification message can besent to notify the subscriber about the SDM Partial Lock successful orfailed) execution. If Okay button is selected, the system will triggerthe partial lock operation at the SDM server, which will perform thepartial lock operations. After the SDM server receives the partial locksuccessful completion confirmation, an UI screen may display with thetransaction confirmation.

As shown by the above discussion, functions relating to the SDMfunctionality may be implemented on computers connected for datacommunication via the components of a packet data network as shown inFIG. 1. Although special purpose devices may be used, such devices alsomay be implemented using, one or more hardware platforms intended torepresent a general class of data processing device commonly used to run“server” programming so as to implement the functions discussed above,albeit with an appropriate network connection for data communication.

As known in the data processing and communications arts, ageneral-purpose computer typically comprises a central processor orother processing device, an internal communication bus, various types ofmemory or storage media (RAM, ROM, EEPROM, cache memory, disk drivesetc.) for code and data storage, and one or more network interface cardsor ports for communication purposes. The software functionalitiesinvolve programming, including executable code as well as associatedstored data, e.g. files used for enabling remote change to theoperational control parameters of the mobile station using SDM andassociated change notification. The software code is executable by thegeneral-purpose computer that fractions as the MDMi 41 server and/orthat functions as a mobile station. In operation, the code is storedwithin the general-purpose computer platform. At other times, however,the software may be stored at other locations and/or transported forloading into the appropriate general-purpose computer system. Executionof such code by a processor of the computer platform enables the term toimplement the methodology for managing a customer's mobile station andproviding a notification of a resultant change, in essentially themanner performed in the implementations discussed and illustratedherein.

FIGS. 5 and 6 provide functional block diagram illustrations of generalpurpose computer hardware platforms. FIG. 7 illustrates a network orhost computer platform, as may typically be used to implement as server.FIG. 8 depicts a computer with user internee elements, as may be used toimplement a personal computer or other type of work station or terminaldevice, although the computer of FIG. 8 may also act as a server ifappropriately programmed. It is believed that those skilled in the artare familiar with the structure, programming and general operation ofsuch computer equipment and as a result the drawings should beself-explanatory.

A server, for example, includes a data, communication interface forpacket data communication. The server also includes a central processingunit (CPU), in the form of one or more processors, for executing programinstructions. The server platform typically includes an internalcommunication bus, program storage and data storage for various datafiles to be processed and/or communicated by the server, although theserver often receives programming and data via network communications.The hardware elements, operating, systems and programming languages ofsuch servers are conventional in nature, and it is presumed that thoseskilled in the art are adequately familiar therewith. Of course, theserver functions may be implemented in a distributed fashion on a numberof similar platforms, to distribute the processing load.

Hence, aspects of the methods of managing a customer's mobile stationand providing a notification of a resultant change outlined above may beembodied in programming. Program aspects of the technology may bethought of as “products” or “articles of manufacture” typically in theform of executable code and/or associated data that is carried on orembodied in a type of machine readable medium, “Storage” type mediainclude any or all of the memory of the computers, processors or thelike, or associated modules thereof, such as various semiconductormemories, tape drives, disk drives and the like, which may providestorage at any time for the software programming. All or portions of thesoftware may at times be communicated through the Internet or variousother telecommunication networks. Such communications, for example, mayenable loading of the software from one computer or processor intoanother, for example, from as management server or host computer of thenetwork operator into the computer platform of the mobile station andthe MDMi server. Thus, another type of media that may bear the softwareelements includes optical, electrical and electromagnetic waves, such asused across physical interfaces between local devices, through wired andoptical landline networks and over various air-links. The physicalelements that carry such waves, such as wired or wireless links, opticallinks or the like, also may be considered as media bearing the software.As used herein, unless restricted to tangible, non-transitory “storage”media, terms such as computer or machine “readable medium” refer to anymedium that participates in providing instructions to a processor forexecution.

Hence, a machine readable medium may take many forms, including but notlimited to, a tangible storage medium, a carrier wave medium or physicaltransmission medium. Non-volatile storage media include, for example,optical or magnetic disks, such as any of the storage devices in anycomputer(s) or the like, such as may be used to implement the SDMfunctionality shown in the drawings. Volatile storage media includedynamic memory, such as main memory of such a computer platform.Tangible transmission media include coaxial cables; copper wire andfiber optics, including the wires that comprise a bus within a computersystem, carrier-wave transmission media can take the form of electric orelectromagnetic signals, or acoustic or light waves such as thosegenerated during radio frequency (“RF”) and infrared (“IR”) datacommunications. Common forms of computer-readable media thereforeinclude for example: a floppy disk, a flexible disk, hard disk, magnetictape, any other magnetic medium, a CD-ROM DVD or DVD-ROM, any otheroptical medium, punch cards paper tape, any other physical storagemedium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave transporting data orinstructions, cables or links transporting such a carrier wave, or anyother medium from which a computer can read programming code and/ordata. Many of these forms of computer readable media may be involved incarrying. One or more sequences of one or more instructions to aprocessor for execution.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended lay the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

What is claimed is:
 1. A method, comprising steps of: communicating overthe air through a mobile communication network with a subscriber devicemanagement application running on a customer's mobile station; causingthe subscriber device management application to change an operationalcontrol parameter of the customer's mobile station, via the over the aircommunication; in response to the change of the operational controlparameter of the customer's mobile station, accessing data of asubscriber containing preference information; locating in the subscriberdata, notification language, wherein the notification language isrelated to the operational control parameter changed by the subscriberdevice management application; generating, using the notificationlanguage, a mobile messaging service message to notify a subscriber ofthe change to the operational parameter; and sending the generatedmobile messaging service message containing a notification of the changeof the operational control parameter to a mobile directory numberassociated with another mobile station.
 2. The method of claim 1,further comprising: retrieving from the subscriber data the mobiledirectory number associated with the other mobile station.
 3. The methodof claim 1, further comprising steps of: in response to a query,receiving information that confirms a customer has authority to changesettings to a mobile service provider account corresponding to themobile station; and prior to sending the generated mobile messagingservice message to the mobile directory associated with the other mobilestation, obtaining, via a customer input, information sufficient toidentify to the mobile service provider the other mobile device.
 4. Themethod of claim 1, further comprising: sending instructions causing auser prompt to be presented on a display of a user device, wherein theuser device is different from the customer's mobile station and theprompt requests a user input to confirm the change in operationalcontrol parameter; in response to an input confirming the change of theoperational parameter, delivering an instruction to change the operationcontrol parameter to the subscriber device management application on thecustomer's mobile station; and presenting on the user device display ascreen indicating confirmation of the change of the operationalparameter.
 5. The method of claim 4, wherein the user device display isa display on a point of sale device or a display presented on a customerservice representative system.
 6. The method of claim 1, furthercomprising: informing a customer of a mobile service provider via adisplayed prompt that the change of the operational control parameter ofthe mobile station incurs a charge to a bill associated with thecustomer, the customer associated with the mobile station; and inresponse to the prompt, receiving a customer confirmation input that theimpending change to the operational control parameter is to be chargedto the bill.
 7. The method of claim 1, further comprising: informing acustomer of a mobile service provider via a displayed prompt that thechange of the operational control parameter of the mobile station isfree of charge to a bill associated with the mobile station, thecustomer associated with the mobile station; and in response to theprompt, receiving a customer confirmation input that the impendingchange to the operational control parameter is to be made free ofcharge.
 8. The method of claim 1, wherein the operational parameterchange is at least one of a partial lock of the mobile station, aturning On or Off of a Wi-Fi capability of the mobile station, a turningOn or Off of a built-in camera of the mobile station, a preventing ofaccess to personal data stored in the mobile station, a wiping outcontent of the mobile station, wherein the partial lock of the mobilestation allows the mobile station to perform one or more of ringing,vibrating, receiving incoming calls, making and receiving emergencycalls, and making calls to a service provider customer service.
 9. Ahost system, comprising: a processing device; and a non-transitory,machine readable storage medium containing executable programinstructions embodied in the machine readable storage medium forexecution by processing device, wherein execution of the programinstructions causes the processing device to perform functionscomprising: communicating over the air through a mobile communicationnetwork with a subscriber device management application running on acustomer's mobile station; causing the subscriber device managementapplication to change an operational control parameter of the customer'smobile station, via the over the air communication; in response to thechange of the operational control parameter of the customer's mobilestation, accessing data of a subscriber containing preferenceinformation; locating in the subscriber data, notification language,wherein the notification language is related to the operational changeparameter changed by the subscriber device management application;generating using the notification language a mobile messaging servicemessage to notify the subscriber of the change to the operationalparameter; and sending the generated mobile messaging service messagecontaining a notification of the change of the operational controlparameter to a mobile directory number associated with another mobilestation.
 10. The host system of claim 9, wherein execution of theprogram instructions causes the processing device to perform functionsfurther comprising: accessing subscriber data containing user preferenceinformation retrieving from the subscriber data the mobile directorynumber associated with the other mobile station.
 11. The host system ofclaim 9, wherein execution of the program instructions causes theprocessing device to perform functions further comprising: in responseto a query, receiving information that confirms a customer has authorityto change settings to a mobile service provider account corresponding tothe mobile station; and prior to sending the generated mobile messagingservice message to the mobile directory associated with another mobilestation, obtaining, via a customer input, the information sufficient toidentify of the other mobile device to the mobile service provider. 12.The host system of claim 9, wherein execution of the programinstructions causes the processing device to perform functions furthercomprising: sending instructions causing a user prompt to be presentedon a display of a user device, wherein the user device is different fromthe customer's mobile station and the prompt requests a user input toconfirm the change in operational control parameter; in response to aninput confirming the change of the operational parameter, delivering aninstruction to change the operation control parameter to the subscriberdevice management application on the mobile station; and presenting onthe user device display a screen indicating confirmation of the changeof the operational parameter.
 13. The host system of claim 12, whereinthe user device display is a display on a point of sale device or adisplay presented on a customer service representative system.
 14. Thehost system of claim 9, wherein execution of the program instructionscauses the processing device to perform functions further comprising:informing a customer of a mobile service provider that the change of theoperational control parameter of the mobile station incurs a charge to abill associated with the mobile station, the customer associated withthe mobile station; and receiving customer confirmation that theimpending change to the operational control parameter is to be chargedto the bill.
 15. The host system of claim 9, wherein execution of theprogram instructions causes the processing device to perform functionsfurther comprising: informing a customer of a mobile service providerthat the change of the operational control parameter of the mobilestation is free of charge to a bill associated with the mobile station,the customer associated with the mobile station; and receiving customerconfirmation that the impending change to the operational controlparameter is to be made free of charge.
 16. The host system of claim 9,wherein the operational parameter change is at least one of a partiallock of the mobile station, a turning On or Off of a Wi-Fi capability ofthe mobile station, a turning On or Off of a built-in camera of themobile station, a preventing of access to personal data of the customerstored in the mobile station, a wiping out content of the mobilestation, wherein the partial lock of the mobile station allows themobile station to perform one or more of ringing, vibrating, receivingincoming calls, making and receiving emergency calls, and making callsto a service provider customer service.